Mark the experimental property as deprecated
#28811
Conversation
github-actions
bot
added
schema
|
Tip: Review these changes grouped by change (recommended for most PRs), or grouped by feature (for large PRs). |
|
|
||
| - `experimental`: a `boolean` value. | ||
|
|
||
| **Warning**: The `experimental` property is deprecated. Prefer using more well-defined stability calculations, such as Baseline, instead. |
There was a problem hiding this comment.
| **Warning**: The `experimental` property is deprecated. Prefer using more well-defined stability calculations, such as Baseline, instead. | |
| > [!WARNING] | |
| > The `experimental` property is **deprecated**. | |
| > Prefer using better defined stability calculations, such as Baseline, instead. |
There was a problem hiding this comment.
Unfortunately, this won't work. GitHub's (non-standard, unspecified 🙄) admonitions don't work in a list. They only render if the > is at column 1.
Co-authored-by: Claas Augner <[email protected]>
Co-authored-by: Claas Augner <[email protected]>
github-actions
bot
added
size:s
BCD tables on MDN show an icon for experimental features. We could instead show a Baseline icon, but we would probably have to compute it directly from each BCD feature, without taking into consideration web-features. I would propose to add this computed Baseline status per BCD feature into the published BCD data, and to do this at the same time of deprecating experimental. |
caugner
left a comment
caugner
left a comment
There was a problem hiding this comment.
We should wait with the deprecation until we provide a per-feature replacement of the experimental status, see my previous comment.
|
I don't think we should wait. This advice would be to new consumers of BCD: they should not use |
3 participants
Summary
Consumers of BCD probably shouldn't use the
experimentalfield.Test results and supporting details
In the October 21, 2025 BCD meeting, I suggested this as a possibility. I'm finally getting around to it!
Related issues
n/a